Skip to content

Fix aggregated results not displaying on Chrome#461

Merged
paulapreuss merged 2 commits intomainfrom
fix/browser-specific-issues
Apr 22, 2026
Merged

Fix aggregated results not displaying on Chrome#461
paulapreuss merged 2 commits intomainfrom
fix/browser-specific-issues

Conversation

@paulapreuss
Copy link
Copy Markdown

Fixes #418. Apparently, Chromium is a lot more strict with input_type="number" and will parse as invalid if the value uses comma as a decimal separator, which was causing some numbers to not display in the result assets when clicking them open.

As the values are just meant for checking and readonly, it seems fine to just remove the input_type constraint from the fields, which allows the numbers to be displayed.

Interestingly, this issue was only happening when using the german version of open plan (/de locale), because here the decimal separator gets parsed as a comma. When using /en, the decimal separator is a point and did not cause any issues in the display.

@paulapreuss paulapreuss merged commit 0ca0fdb into main Apr 22, 2026
2 checks passed
@paulapreuss paulapreuss deleted the fix/browser-specific-issues branch April 22, 2026 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Results do not get properly filled in for asset modals using Chrome

2 participants